Description

Fixes ISXB-1171.

The issue was caused by the on change handler causing a full UI rebuild of the editor window when it was not required. The fix required added a new enum which told the UI system if a rebuild was necessary - defaulting to rebuilding since this was the previous default.

Testing status & QA

This was tested locally using the provided project. The change is localised to the composite binding part of the window and so I don't believe additional QA would be required.

Overall Product Risks

• Complexity: 0
• Halo Effect: 0

Comments to reviewers

The only concern I have with this solution is - do we know of any instances where changes to the UI would require a complete rebuild?

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.